PD Collection CD 1

home *** CD-ROM | disk | FTP | other *** search

/ PD Collection CD 1 / PD Collection CD 1.iso / textual / tex / files / !tex / TeXsource / beebe / hlp / dvi next >

Wrap

Text File | 1986-12-27 | 35.1 KB | 793 lines

DVIxxx - Display TeX DVI Files on Assorted Output Devices [26-Dec-86] SYNOPSIS Several TeX DVI translators are available. They all expect the name of the .DVI file on the command line, and the extension .DVI can always be omitted. As illustrated below (extracted from a PHOTO log), they issue a one-line identifier message and, if no command line arguments are given, type a Unix-style ``usage'' message. Some of them may have additional help files (*note: SEE ALSO. section below). On case-sensitive file systems, file names may be expected to be entirely in lower case, so you should should type ``dvialw'' instead of ``DVIALW''. For all except DVIBIT (which is intended for interactive display), the output file will be given the name of the .DVI file, but extension .DVI-xxx, where xxx is the three-character mnemonic for the translator program. For DVIBIT, output is on ``stdout'' which defaults to the terminal; it may be redirected in the usual Unix fashion by ``>filename'' on the command line (e.g. @DVIBIT foo >foo.out). As the .DVI file is processed, a list of errors is printed on the standard error unit ``stderr'', this list is also saved in a file with extension .DVI-LOG. This file is not created if there are no errors. As each page is printed, the physical page number and the TeX page number is printed without a following character return; after the last page, the string `` [OK]'' is printed, followed by a carriage return. This gives a convenient progress report to the terminal. If it is not wanted, then the error output can be redirected into a file (possibly the null device) (e.g. @DVIxxx foo &foo.err), or the ``-q'' option can be given to suppress it. The order of command options and DVI file names is not significant; all switch values apply to all DVI files. DVI files are processed in order from left to right. The available translators are as follows: DVIALW PostScript (Apple LaserWriter) DVIDOC Very rough printer image of a DVI file DVIBIT Version 3.10 BBN BitGraph terminal DVIGD Golden Dawn Golden Laser 100 printer DVIIMP Imagen imPRESS-language laser printer family DVIJET Hewlett-Packard Laser Jet DVIJEP Hewlett-Packard Laser Jet Plus DVIM72 Apple Imagewriter 72 dpi printer DVIMAC Apple Imagewriter 144 dpi printer DVIMPI MPI Sprinter 72 dpi printer DVIO72 OKIDATA Pacemark 2410 72 dpi printer DVIOKI OKIDATA Pacemark 2410 144 dpi printer DVIPRX Printronix 60h x 72v dpi printer DVITOS Toshiba P-1351 180 dpi printer DVITYP or DVITYPE DVI Translator for human-readable output SAMPLE-EXECUTION A sample execution of LATEX and DVIALW from a PHOTO log is as follows: @latex biblio.ltx This is TeX, Tops-20 Version 1.1 (preloaded format=lplain 84.9.29) (APS:<BEEBE.PLOT79.DOCUMENTATION>BIBLIO.LTX.28 LaTeX Version 2.06a - Release 7 July 84 (APS:<TEX.LATEX>REPORT.STY.2 Document Style 'report'. Version 0.91 - released 25 June 1984 (APS:<TEX.LATEX>REP11.STY.2)) (APS:<BEEBE.PLOT79.DOCUMENTATION>MYBIBLIO.STY.1 Mybibliography environment style - Version 0.0 - 15-May-86) (APS:<BEEBE.PLOT79.DOCUMENTATION>BIBLIO.AUX.12) [0] (APS:<BEEBE.PLOT79.DOCUMENTATION>BIBLIO1.LTX.3 [1] [2] [3] [4] [5]) [6] (APS:<BEEBE.PLOT79.DOCUMENTATION>BIBLIO.AUX.13) (see the transcript file for additional information) Output written on APS:<BEEBE.PLOT79.DOCUMENTATION>BIBLIO.DVI.1 (7 pages, 13960 bytes). Transcript written on APS:<BEEBE.PLOT79.DOCUMENTATION>BIBLIO.LST.1. @dvialw -x0.3in -y0.2in biblio bt:example [TeX82 DVI Translator Version 2.0 for PostScript [Apple LaserWriter laser printer]] [Input from DVI file biblio.dvi] [Output on file biblio.dvi-alw] [7 pages] [1500 magnification] [7{6}] [6{5}] [5{4}] [4{3}] [3{2}] [2{1}] [1{0}] [OK] [Input from DVI file bt:example.dvi] [Output on file bt:example.dvi-alw] [1 pages] [1500 magnification] [1{1}] [OK] When the TOPS-20 version of TeX finishes execution, it normally simulates terminal input of a line of the form TeXspool: dvifile without supplying a final carriage return. The default value of the logical name TeXspool: points to a dummy program which does nothing, so if you just type a carriage return yourself, the line is effectively ignored. This is reasonable in that it usually takes several trips through TeX before you have a ``.dvi'' file worth printing. If you like, you can redefine ``TeXspool:'' to point to your favorite DVI translator, for example, define TeXspool: sys:dvialw.exe Then when you type a carriage return when TeX finishes, it will run the translator immediately, saving you a line of typing. If you do not want the translator to run, just cancel the line by typing CTL-U or CTL-C. A sample invocation of DVITYPE is as follows: @dvitype DVIFILE : dvifile OUTPUT : tty: This is DVItype, Tops-20 Version 2.6 Output level (default=3, ? for help): Starting page (default=*): Maximum number of pages (default=1000000): Assumed device resolution in pixels per inch (default=240/1): New magnification (default=0 to keep the old one): Options selected: Starting page = * Maximum number of pages = 1000000 Output level = 3 (the works) Resolution = 240.00000000 pixels per inch numerator/denominator=25400000/473628672 magnification=1000; 0.00005067 pixels per DVI unit ' TeX output 1984.09.29:2210' Postamble starts at byte 23408. maxv=40763392, maxh=26738688, maxstackdepth=9, totalpages=9 Font 73: amcsc10---loaded at size 655360 DVI units Font 72: amcsc10---loaded at size 1132462 DVI units (this font is magnified 173%) ...and so on... DESCRIPTION These drivers are written in C, and with C preprocessor conditional compilation features, are all derived from one master set of files, so that there is substantial code sharing among them. Host machine and output device dependencies are parametrized to allow easy movement to new hosts and new output devices. Implementations now exist on Gould Unix, Hewlett-Packard Unix, PC-DOS, TOPS-20, VAX Unix, and VAX VMS, with others in progress. The command options are (letter case is IGNORED): -a Implement virtual font caching, if possible. When a font file is opened, a buffer is allocated to contain the entire file, and the file is then read with one system call. This is important primarily on networked file systems, where the many random-access calls in the font file for small amounts of data entail substantial network overhead. With the entire file cached in local memory, this overhead is removed. The additional memory required for the font file buffers amounts to 100K to 200K bytes (assuming the compact .PK font file format), which is not excessive. If memory cannot be allocated for a font file, then normal buffering of small blocks is used. A trace option (-d64) is provided to monitor the font caching; see below. -b Backwards order printing from the default. For example, laser printers using the Canon engine print normally receive pages in reverse order because they stack printed side up. Some have page handling mechanisms that stack them face down, and in such a case -b will ensure that they come out in order 1,2,... instead of n,n-1,n-2,... -c# Print # copies of each output page. Page copies are printed consecutively; this does NOT give multiple collated copies of the entire job. -d# Produce debugging output on ``stderr'' if a non-zero value is given. Only the last switch given is used. Add values of the following possible options to obtain the switch value: 1 (DVIJET only) print page bitmap in hexadecimal; 2 display page coordinates and metrics of each output character, and print each character bitmap in hexadecimal; 4 (DVIJEP only) display updated page coordinate of each character after each call to ``fixpos()''; 8 print filename and open mode of each SUCCESSFUL file opening; 16 print filename and open mode of each UNSUCCESSFUL file opening; 32 show discarded off-page text; 64 trace virtual font caching. For example, -d24 will trace all attempted file openings. -eVAR=value Define an environment variable on the command line (see the later section ENVIRONMENT VARIABLES). The acceptable values for VAR are DVIHELP, FONTLIST, TEXFONTS, and TEXINPUTS. Under normal use of the Translators, these can be set by TOPS-20 and VAX VMS ``define VAR: value'' commands, or by Unix ``csh'' ``setenv VAR=value'' or ``sh'' ``VAR=value'' commands. When the translator is invoked by another program, such as a print spooler, on some systems it may not be possible to set a particularly value of an environment variable for the subprocess, so this option gets around this limitation. On most Unix systems, it should be possible to use the call ``system("VAR=value; dvixxx filename")''. -ffontsubfile Define an alternate font substitution file which is to be used instead of the default ones (see below). -l Inhibit logging. -m# Reset magnification to #. The default for low resolution printers is ``-m579'', corresponding to (1/1.2**3) magnification. By TeX conventions, magnification 1000 corresponds to a 200-dot/inch output device. The default magnification is always adjusted according to the output device resolution in order to give a normal page size, so this parameter should rarely be required. Legal values are int((1000 or 1440 or 1500)*(1.2)**(k/2)) (k = -16,16); other values will be set to the nearest in this family. Not all fonts will be available in this wide range, and most installations will probably have only a half dozen or so magnifications. -o# and -o#:# and -o#:#:# Specify a page number, or range of page numbers, to be selected for output. In the third form, the last number is the page number step size; it is normally 1. This option may be specified any number of times. If it is not specified, then all pages will be printed. Pages are numbered in order 1,2,3,... in the file, but any page number recorded by TeX on the printed page will in general be different. Negative page numbers count backward; -1 is the last page in the document, -2 the second last page, and so on. As pages are selected for printing, ``[#{#}'' will be printed on ``stderr'', where the first is the page number in the file, and the second is the value of the TeX counter, \count0, which usually records the printed page number. When the page is completely output, a closing ``]'' will be printed on ``stderr''. Any error messages from processing of that page will therefore occur between the square brackets. For example, ``-o1:3 -o12 -o17:23 -o-3:-1'' would select pages 1, 2, 3, 12, 17, 18, 19, 20, 21, 22, and 23, plus the last three pages. Pages will always be printed in an order appropriate for the device so that the first document page occurs first face up in the document stack; the ``-b'' option can be used to reverse this order. For example, some Hewlett-Packard Laser Jet Plus printers are equipped with a page flipper which stacks output face down; for these, the ``-b'' option will ensure that the pages come out in the expected order. Specification of a page number step size is useful for producing duplex (two-sided) printing. For example, with laser printers using the Canon LBP-CX engine, the first run could specify ``-o1:9999:2'', which would stack output face up, beginning with the last page, and ending with page 1 on top. The printed pages can then be reinserted in the input tray FACE UP, page 1 on the top, exactly as they were found in the output tray, with the top of the page in the tray closest to the end which is inserted first into the printer. A second run with ``-b -o2:9999:2'' would then print pages 2, 4, ..., on the backs of pages 1, 3, ...; note the ``-b'' option to get backwards order on the second run. There is a bug in Microsoft C's ``sscanf()'' on the IBM PC; it does not correctly parse input on the format "%d:%d:%d" in ``option()'' for the page number switch. It correctly returns the numbers, but instead of returning the number of such items parsed, it returns -1, which should only happen if none are parsed. A work around seems to be to supply a trailing colon on the switch, so that you write ``-o17:'' instead of ``-o17''. -p Inhibit font preloading. This may produce output a few seconds earlier when all pages are output, but should have negligible effect on the execution time, and consequently, should normally not be specified. When individual pages are being printed with the -o# option, preloading is necessary (and will be forced) to ensure that all fonts are defined before they are referenced. -q Quiet mode. Status displays to ``stderr'' are suppressed, unless warning or error messages are issued. -r# (Device = HP Laser Jet only). Specify the Laser Jet output resolution in dots per inch. ``#'' must be one of 75, 100, 150, or 300. The actual plot file is identical in each case; only the size on the output page is changed, because the resolution change is effected by printing 1 x 1, 2 x 2, 3 x 3, or 4 x 4 pixel blocks. -r (Device = Golden Laser 100 only). Select run-length encoding of the output file. This reduces disk space typically by 10% to 40%, but increases host CPU time for the preparation of the output file. -r (Device = Apple ImageWriter only). Select run-length encoding of the output file. -r (Device = Toshiba P-1351 only). Select run-length encoding of the output file. This reduces disk space typically by 10% to 40%, but increases host CPU time for the preparation of the output file, and because of poor logic in the printer, may double the print time! The print quality is also substantially worse, so this option is generally NOT recommended. -s# (Device = Apple LaserWriter only). Force characters larger than # pixels wide or high to be reloaded each time they are required. The Version 23.0 PostScript interpreter has a bug which manifests itself in fatal ``VM error'' messages when large characters are sent. A reasonable default value has been set for this which should normally avoid the problem. Specifying ``-s0'' will cause reloading of every character each time it is used. -v (Device = Apple LaserWriter only). Force reloading of all required fonts at start of each page. -x#bp big point (1in = 72bp) -x#cc cicero (1cc = 12dd) -x#cm centimeter -x#dd didot point (1157dd = 1238pt) -x#in inch -x#mm millimeter (10mm = 1cm) -x#pc pica (1pc = 12pt) -x#pt point (72.27pt = 1in) -x#sp scaled point (65536sp = 1pt) The ``-x'' options specify the left margin of the TeX page on the output page in any of the indicated units. Letter case is not significant in the unit field, which must not be separated from the number by any space. # may be fractional. For example, ``-x1.0in'', ``-x2.54cm'', ``-x72.27pt'', and ``-x6.0225pc'' all specify a one inch left margin. Negative values are permissible, and may be used to shift the output page left (possibly truncating it on the left) in order to display a wide TeX page. -y# inch -y#bp big point (1in = 72bp) -y#cc cicero (1cc = 12dd) -y#cm centimeter -y#dd didot point (1157dd = 1238pt) -y#in inch -y#mm millimeter (10mm = 1cm) -y#pc pica (1pc = 12pt) -y#pt point (72.27pt = 1in) -y#sp scaled point (65536sp = 1pt) The ``-y'' options specify the top margin of the TeX page on the output page in any of the indicated units. Letter case is not significant in the unit field, which must not be separated from the number by any space. # may be fractional. For example, ``-y1.0in'', ``-y2.54cm'', ``-y72.27pt'', and ``-y6.0225pc'' all specify a one inch top margin. Negative values are permissible, and may be used to shift the output page up (possibly truncating it on the top) in order to display a long TeX page. -z (Device = Apple LaserWriter or HP LaserJet Plus on TOPS-20 only). For each DVI file processed, type in an EXEC command ``DVISPOOL: dvifilename'' followed by a newline; the user may then define DVISPOOL: to be a program which sends the translation of the DVI file to the appropriate output spooler. If no ``-ffontsubfile'' option is given, and font substitution is required, if the current DVI file is foo.dvi, then the files ``foo.sub'', ``texfonts.sub'', and ``texinputs:texfonts.sub'' will be tried in order. The first two will be found on the current directory, and the last is the system default. This gives the option of document-specific, user-specific, and system-specific substitutions, and the ``-f'' option allows all of these to be overridden. Font substitution lines have the form: % comment oldname.oldmag -> subname.submag % comment oldname oldmag -> subname submag % comment oldname -> subname % comment Examples are: % These provide replacements for some LaTeX invisible fonts: iamr10 1500 -> amr10 1500 % comment iamr10.1500 -> amr10.1500 % comment iamssb8 -> amssb8 % comment The first two forms request substitution of a particular font and magnification. The third form substitutes an entire font family; the closest available magnification to the required one will be used. Any dots in the non-comment portion will be converted to spaces, and therefore, cannot be part of a name field. The first matching substitution will be selected, so magnification-specific substitutions should be given first, before family substitutions. Comments are introduced by percent and continue to end-of-line, just as for TeX. One whitespace character is equivalent to any amount of whitespace. Whitespace and comments are optional. SCREEN-CONTROL At present, DVIBIT is the only family member which supports interactive viewing of the TeX output. The following description therefore applies only to it, but the functionality should be adhered to in any new interactive device drivers. All switches, including the page selection (-o) and page origin (-x and -y) switches, work normally. When the end-of-page command is reached in the DVI file, the driver will display at the top of the screen a two-line message containing a help menu and the current page numbers in the document, then pause for terminal input. Any typeahead is flushed before reading input to make sure the user is synchronized with the display, and any illegal input is discarded with a warning beep. The input can select * redisplay of the current page, possibly shifting it up, down, left, or right, to see more of it, or to restore a display trashed by an unexpected system message or transmission line error; * continuation to the next page in the page list selected by default or by the -o option; * backing up to the previous page (useful if you overshoot); * display of an arbitrary page by typing its sequence number; * termination of execution. Although the menu bar on the top line displays only a subset of the possible commands, a number of synonyms are provided for user convenience. In particular, arrow keys in VT52 and VT100 modes are recognized, as are EMACS control-character commands to move the cursor or page display. The display shifts by a quarter of its height or width in response to an up, down, left, or right movement command. Here is the current command list. For single-letter commands, letter-case is not significant. In most implementations, input is immediate; no terminating carriage return is necessary. Consequently, typing error correction is supported only for the digit string command. arrow keys Move the display up, down, left, or right. D or CTL-N Move the display down. U or CTL-P Move the display up. L or CTL-B Move the display left. R or CTL-F Move the display right. . or CTL-L Redisplay current page. CARET or BACKSPACE Redisplay previous page. nnn nnn is a digit string; DELETE/RUBOUT and BACKSPACE keys correct typing errors in it. Move to nnn-th page, where document pages are numbered 1, 2, .... The TeX page numbers are displayed under the menu bar. This is a recursive display; if you respond at end-of-page with a next-page command, display will revert to the page sequence you were viewing when you first issued the nnn command. SPACE or RETURN or CTL-V Display next page. Q or X Quit or exit. The screen will be cleared and the terminal restored to its normal font and emulation mode. SPECIALS The TeX \special command is intended to allow the specification in a ``.TEX'' file of a request to the DVI driver, usually for the insertion of graphical material at that point in the document. It is currently implemented only for DVIALW; other drivers will simply issue a warning message. The TeX \special command is expected to look like \special{overlay filename} % absolute positioning or \special{include filename} % relative positioning or \special{insert filename} % relative positioning In the first case, the PostScript file to be included will be mapped onto the page at precisely the coordinates it specifies. In the other two cases, the upper-left corner of the bounding box will be placed at the current point. The PostScript file must then contain (usually near the start) a comment of the form %%BoundingBox: llx lly urx ury specifying the bounding box lower-left and upper-right coordinates in standard PostScript units (1/72 inch). Alternatively, if the comment %%BoundingBox: (atend) is found in the file, the last 1000 characters of the file will be searched to find a comment of the form: %%BoundingBox: llx lly urx ury If the PostScript file cannot be opened, or the \special command string cannot be recognized, or for relative positioning, the bounding box cannot be determined, a warning message is issued and the \special command is ignored. Otherwise, the section of the PostScript file between the comment lines %begin(plot) %end(plot) is copied to the output file surrounded by save 300 72 div 300 72 div scale % revert to standard 1/72 inch units (xcp(in 1/72in)-llx) (ycp(in 1/72in)-ury) translate % if relative positioning ...PostScript file contents... restore Plot files produced by <PLOT79> have all the expected commands in them to allow their use in TeX \special commands. The two <PLOT79> parameters which influence the size of the plot are * the device size specified in the call to SETSZ(); it defaults to 11in if SETSZ is not called. * the device space specified in the call to SETDS2() or SETDS3(); it defaults in the CORE system to the unit square, but if the <PLOT79> framing routines are called, they will reset the device space to a horizontal or vertical frame in proportions of the local standard paper size ($1 : 8.5/11$ in the USA). For example, if a device size of 5in is specified for a standard horizontal frame, the bounding box will be declared to be 5in wide and (8.5/11.0)*5 = 3.8636in high, so a TeX manuscript requiring the plot could have the following commands at the start of a new paragraph: \special{include plotfilename} \vspace*{3.9in} ENVIRONMENT-VARIABLES The behavior of the DVI translators can be influenced by definition of logical names on TOPS-20 and VAX VMS, or environment variables in UNIX and PC-DOS. Compiled-in internal defaults will be provided for any of these which are not defined. The names currently recognized are as follows: DVIHELP This variable defines an alternate help string which is typed when the user makes an input error. It should direct the user to additional documentation. For example, it might be ``try HELP DVI or XINFO DVI''. FONTLIST Normally, the drivers are prepared to search first for .PK, then .GF, then .PXL font files. This variable can be used to change this search order, or remove one or more of the possibilities. It is expected to contain at least one of the strings PK, GF, or PXL, possibly separated by arbitrary punctuation and other text. For example, ``PXL-then-PK-then-GF'', ``PK-GF'', ``PXL'', ``PXL/GF/PK''. TERM This variable is used only for DVIBIT; if it does not evaluate to either ``bitgraph'' or ``bg'', DVIBIT will refuse to run. On Unix, this is the conventional way of defining terminal types with the TERMCAP or TERMINFO systems. TEXFONTS This defines the directory path for finding font files. Its value is prepended to the name of a TeX font to get a full file specification. For example ``cmr10'' on a 300-dot/inch device might correspond on TOPS-20 to the files ``texfonts:cmr10.300gf'', ``texfonts:cmr10.300pk'', or ``texfonts:cmr10.300pxl''. TEXINPUTS This defines the directory path for finding files which are not in the current working directory. It is PREPENDED to file names. IBM-PC-Caveats The latest version of the drivers has been compiled with Microsoft C Version 4.0. With Version 3.0, some ``.dvi'' files experienced a fatal ``floating-point stack overflow'' error both with and without a floating-point coprocessor; this can only be due to code generation errors, and it disappeared with Version 4.0. PC-DOS by default has only a small number of available open files, and this number is not adequate for the drivers with the value of five for ``MAXOPEN'' set in ``machdefs.h''. You need to increase the limits by entering the lines FILES=10 BUFFERS=10 in the ``config.sys'' file in the boot directory, then reboot the system to have the new values take effect. Larger values are of course possible, though ``FILES=20'' is the limit with current versions of PC-DOS. Run-time performance can be quite sensitive to these settings, so you may wish to experiment. If there is no ``config.sys'' file, or the settings of ``FILES'' and ``BUFFERS'' are too small, you will find the disk whirring madly while the driver attempts to open font files with neighboring magnifications, and then it will finally die with a message ``unable to open .err file''. Use of the ``-d24'' option may be useful in tracking how many files can successfully be opened (that is why I added that switch option). The drivers have been loaded with the default Microsoft floating-point library; the compiler generates calls to library routines which test a flag initialized at startup time which indicates the presence or absence of the floating-point coprocessor chip. If it is available, the library routines will automatically use it. You can force the chip to be ignored by defining an arbitrary non-empty string value for the environment variable ``NO87'', for example set NO87=no-8087-available When the DVI translator runs, the value of this variable should be typed on the screen as the first output line. On a Leading Edge PC, this typeout does not appear, for unknown reasons. On my 4.77MHz PC XT, the translators run twice (!) as slowly when ``NO87'' is defined. The reason that you might need to know this is that the method employed by the library routines for detecting the presence or absence of an 8087 (or 80287) chip is not infallible, thanks to design flaws of some PC's and possibly also the Intel chips. It is conceivable that the library might think a coprocessor chip is present, when in fact it is not, and the first floating-point instruction executed would hang the machine. FILES *.dvi TeX DeVice Independent output file *.dvi-log TeX DVIxxx translator error log *.err TeX DVIxxx translator error log when long extensions are not available *.dvi-xxx TeX device-dependent DVI translator output file *.xxx TeX DVIxxx translator output file when long extensions are not available *.sub DVI file-specific font substitution file DVISPOOL: Logical name (TOPS-20 only) defining program which sends translation of DVI file to the appropriate output spooler. texfonts.sub Job-wide font substitution file texfonts:*.*pxl TeX default font rasters texfonts:*.*gf TeX default font rasters texfonts:*.*pk TeX default font rasters texinputs:dvialw.ps PostScript header file containing standard macro definitions prefixed to PostScript output from DVIALW texinputs:texfonts.sub System-wide font substitution file SEE-ALSO dvitype, tex, ``Local LaTeX Guide'', ``A TeX DVI Driver Family''. BUGS None known. AUTHORS David Fuchs at Stanford University wrote DVITYPE in WEB and defined the DVI file format. Mark Senn at Purdue University wrote a preliminary version of the BBN BitGraph driver in C, using DVITYPE as a model. Stephan v. Bechtolsheim and Bob Brown at Purdue, Robert Wells at BBN, and Jim Schaad and Richard Furuta at the University of Washington, improved it. The transformation to about a dozen other device drivers, plus the massive code rearrangement for many new features as well as easy identification of host- and device-dependent sections, as well as support for ``.pk'' and ``.gf'' compact font files, was carried out at the University of Utah by Nelson H.F. Beebe. He also wrote the documents ``A TeX DVI Driver Family'' and ``Using LaTeX at the University of Utah College of Science DEC-20''. The first describes all of these drivers in detail, and the second is the ``Local LaTeX Guide''. Lon Willett at Utah adapted DVIJEP to make DVIIMP for the Imagen laser printer family. Norman Naugle and colleagues at Texas A&M implemented the family on several new systems.